Migrate to new SwiftUI navigation types and make ChatChannel non-optional #31
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This migrates to iOS 16's navigation types (
NavigationSplitView
andNavigationStack
), along with representing the global channel withChatChannel.global
instead ofnil
, since this plays better with the new navigation types1 and is better design anyway. Unfortunately, it is also a breaking change in the protocol, since attaching a channel to messages is now mandatory, since the protocol is considered unstable, however, this shouldn't be too big of an issue.Footnotes
Otherwise the navigation links will appear grayed out ↩